What this adds

A new apply [company] command that drafts written answers to job application screening questions — a workflow distinct from interview prep that wasn't covered by any existing command.

Why it's needed

Job applications increasingly include structured screening questions (behavioral, tools/experience, process/method, "why us"). These are written, not spoken, and require a different register than interview answers. The existing outreach command handles networking messages; apply handles structured application fields.

How it works

7-step workflow:

1. Parse and classify each question (behavioral, process/method, tools/experience, why us)
2. Check job-search/ for prior answers to similar questions — builds a reusable library across applications
3. Gap check before drafting — verifies storybank or resume contains evidence; flags missing evidence rather than fabricating
4. Story selection — presents 2-3 candidate stories per question with a [Domain match] flag when a story comes from the same industry as the target company
5. Draft answers in written register (150-200 words, tighter than spoken interview answers)
6. Output as ready-to-paste block labeled by question
7. Save to job-search/[company]_application.md

Integration with existing skill

• Pulls storybank from coaching_state.md (same pattern as other commands)
• Domain match flag uses the JD/company industry to weight story selection — a story from background verification told to a background verification company lands differently
• Saves follow the same pattern as other commands
• Does not overlap with outreach.md (outreach = networking messages; apply = structured screening question answers)

Files changed

• references/commands/apply.md — new command workflow
• SKILL.md — apply added to Command Registry, Mode Detection (rule 20), and State Update Triggers
• README.md — apply added to Commands table, workflow example (Pre-launch improvements: README, analyze bridge, progress health #11), repository structure, and Best Results tips